-
-
Notifications
You must be signed in to change notification settings - Fork 188
chore: update links to learn.svelte.dev #602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Hm. I have really mixed feelings about rewriting history in blog posts. I don't know what to do about this. https://svelte.dev/blog/svelte-4, for example, contrasts learn.svelte.dev with the old tutorial that's still available for certain browsers. Do we update that too now that that distinction no longer exists? |
Yeah. I think blog posts have multiple functions. I think this helps with SEO and helps with folks who stumble upon these blog posts now trying to learn how to do something. It might hurt for folks who are trying to act as historians and for some reason needed to know that the tutorial used to live on a separate domain (though I did leave some of those references alone). I'm prioritizing the needs of current users over historians here
Yeah, good idea |
I fixed the merge conflicts on this. I tried to be judicious about which links and text to update. Happy to revert a couple more if you think that's best. There are a couple in the last post that would otherwise be broken that I definitely think we should update |
Isn't this what redirects are for? |
I expect there's a negative SEO impact to passing on page rank if you route it through a redirected subdomain. Plus, we have a lot of broken and missing redirects right now: #619 |
I wouldn't worry too much about SEO — if you google 'svelte tutorial' then the top result is the correct one. And it's not like these specific links are broken in the first place |
The links in apps/svelte.dev/content/blog/2023-09-20-runes.md are broken We don't really have anything preventing us from breaking redirects, but if we write these as paths instead of fully qualified URLs then we get the benefit of the link checking. Plus, we've rewritten probably several hundred URLs at this point and these are like the last dozen remaining |
apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md
Outdated
Show resolved
Hide resolved
….0.md Co-authored-by: Rich Harris <rich.harris@vercel.com>
while most these would be redirected, this is likely better for SEO. it also fixes a broken link, which alerted me to another set of redirects I need to double check in a follow up